Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8af09917cfda90c5d90f27c18bbe45d6492fa5bf3824c91e996258948097ec0e

Tx prefix hash: cd3896c4ecf6027d0bdbe13aa1c3246b664218786ff450fa78e2a532a43399c3
Tx public key: 367fd3a7ad0fd4368e7c61bea27bb236fab74acf6ac791fd27b1a0e0d27831ac
Timestamp: 1704254397 Timestamp [UCT]: 2024-01-03 03:59:57 Age [y:d:h:m:s]: 01:129:06:37:14
Block: 927005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353530 RingCT/type: yes/0
Extra: 01367fd3a7ad0fd4368e7c61bea27bb236fab74acf6ac791fd27b1a0e0d27831ac02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ee2db32c5ebf3dc30029e0f00ba1de72688a8aed199c497e2216476d71b55ad 0.600000000000 1384805 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": 927015, "vin": [ { "gen": { "height": 927005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ee2db32c5ebf3dc30029e0f00ba1de72688a8aed199c497e2216476d71b55ad" } } ], "extra": [ 1, 54, 127, 211, 167, 173, 15, 212, 54, 142, 124, 97, 190, 162, 123, 178, 54, 250, 183, 74, 207, 106, 199, 145, 253, 39, 177, 160, 224, 210, 120, 49, 172, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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