Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aec000b7169fc7e207f2cc629780d1937cb1df5ed9ca23cde710268d678cf5d4

Tx prefix hash: 95331e17970bbfa541e2a5b009ecc95cef1c9512b7f3b46fd424578faecfc2a0
Tx public key: 2b42e682a8814b1a54d598ce3aff063ce39302ea2e13a910de561968f5dc30cf
Timestamp: 1734840025 Timestamp [UCT]: 2024-12-22 04:00:25 Age [y:d:h:m:s]: 00:005:09:41:41
Block: 1180506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3822 RingCT/type: yes/0
Extra: 012b42e682a8814b1a54d598ce3aff063ce39302ea2e13a910de561968f5dc30cf02110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3f830b11f9e44782c837021ced3acecd2d1c54ae50493fe3878f96d3bf7e5a4 0.600000000000 1666917 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": 1180516, "vin": [ { "gen": { "height": 1180506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3f830b11f9e44782c837021ced3acecd2d1c54ae50493fe3878f96d3bf7e5a4" } } ], "extra": [ 1, 43, 66, 230, 130, 168, 129, 75, 26, 84, 213, 152, 206, 58, 255, 6, 60, 227, 147, 2, 234, 46, 19, 169, 16, 222, 86, 25, 104, 245, 220, 48, 207, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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