Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5e883716237e1c4f5a514d7659ee8a6559189363235073dc0e37dda84652451

Tx prefix hash: 32646f1ff9d1072ad34c6f8fe06b1888318471dd05c728a6f80f674a7b4fdd3b
Tx public key: 78e9be50edeaed4107f9377453c5069df4de6e24d0376db528033d4f1c2c7b79
Timestamp: 1704164820 Timestamp [UCT]: 2024-01-02 03:07:00 Age [y:d:h:m:s]: 01:099:12:31:24
Block: 926268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332240 RingCT/type: yes/0
Extra: 0178e9be50edeaed4107f9377453c5069df4de6e24d0376db528033d4f1c2c7b790211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d1271868bad85df7e0e70e22c295c22ef7d10750c41e9b2b3a657cb63790aa8 0.600000000000 1384044 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": 926278, "vin": [ { "gen": { "height": 926268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d1271868bad85df7e0e70e22c295c22ef7d10750c41e9b2b3a657cb63790aa8" } } ], "extra": [ 1, 120, 233, 190, 80, 237, 234, 237, 65, 7, 249, 55, 116, 83, 197, 6, 157, 244, 222, 110, 36, 208, 55, 109, 181, 40, 3, 61, 79, 28, 44, 123, 121, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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