Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77e22d132693bea3fbfc48deee563e43de87e1d4185fc10de4b1635e40b9a01b

Tx prefix hash: 1f2d4449def4f1ec46aeada5615c338b678691819dcdbe74e30ff3fa82b91459
Tx public key: 2f8a96502b993c23b5c666ad85edb3a7691d225c65d3db9c60346c4c124af909
Timestamp: 1702469512 Timestamp [UCT]: 2023-12-13 12:11:52 Age [y:d:h:m:s]: 01:152:02:06:57
Block: 912237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369836 RingCT/type: yes/0
Extra: 012f8a96502b993c23b5c666ad85edb3a7691d225c65d3db9c60346c4c124af90902110000000733af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9ae832a1b91262e03754072ed294f1c14098465ad0d319f491a55daaec02346 0.600000000000 1369463 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": 912247, "vin": [ { "gen": { "height": 912237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9ae832a1b91262e03754072ed294f1c14098465ad0d319f491a55daaec02346" } } ], "extra": [ 1, 47, 138, 150, 80, 43, 153, 60, 35, 181, 198, 102, 173, 133, 237, 179, 167, 105, 29, 34, 92, 101, 211, 219, 156, 96, 52, 108, 76, 18, 74, 249, 9, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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