Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a9e26925392f791d200f4d23dc4b6614d5bd6df1fed338bdcfa7736e575c340a

Tx prefix hash: 24d7fc303c3dc0e98a6680b392063ecbb3f62d2e17db01b91ce5a1cf11fc397b
Tx public key: a91797edd03cbe72177513e00f99da6d72b6beee700a5e7128a6d05a18abb334
Timestamp: 1702607644 Timestamp [UCT]: 2023-12-15 02:34:04 Age [y:d:h:m:s]: 01:158:10:50:11
Block: 913358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374423 RingCT/type: yes/0
Extra: 01a91797edd03cbe72177513e00f99da6d72b6beee700a5e7128a6d05a18abb33402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cdda7b6d4b5f3b8b03106f2bb17d1cf58791b20a8a4ff62307003f141a41d35 0.600000000000 1370626 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 913368, "vin": [ { "gen": { "height": 913358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cdda7b6d4b5f3b8b03106f2bb17d1cf58791b20a8a4ff62307003f141a41d35" } } ], "extra": [ 1, 169, 23, 151, 237, 208, 60, 190, 114, 23, 117, 19, 224, 15, 153, 218, 109, 114, 182, 190, 238, 112, 10, 94, 113, 40, 166, 208, 90, 24, 171, 179, 52, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8