Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8c0e12199e0702a8b1069fcbbd2f9e31711f21a04e019958e5e9a2b10cccd26

Tx prefix hash: fa3fd2b47a59950f83dc24de920263408d4562f1796deb7341ce4f0c770f056f
Tx public key: 317ec8031424f53c5e1981796d512e7fdb59a15efceaa573f8c840c48d336dc2
Timestamp: 1740323676 Timestamp [UCT]: 2025-02-23 15:14:36 Age [y:d:h:m:s]: 00:226:14:04:30
Block: 1225582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159638 RingCT/type: yes/0
Extra: 01317ec8031424f53c5e1981796d512e7fdb59a15efceaa573f8c840c48d336dc2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6091dab5e82ca18e23f1672e45a0de0e16976ac90b7005a52b2f54e8269ec50e 0.600000000000 1712449 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": 1225592, "vin": [ { "gen": { "height": 1225582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6091dab5e82ca18e23f1672e45a0de0e16976ac90b7005a52b2f54e8269ec50e" } } ], "extra": [ 1, 49, 126, 200, 3, 20, 36, 245, 60, 94, 25, 129, 121, 109, 81, 46, 127, 219, 89, 161, 94, 252, 234, 165, 115, 248, 200, 64, 196, 141, 51, 109, 194, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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