Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e15fdb39a8bcf125cd5a9be1154a964fcf60a991921848c0a3adc27d13ab4d7c

Tx prefix hash: 813a394512544f4539c2ca903a800c54ea5b079da485a8a2fc7f5ef7a6cf191a
Tx public key: f2bc5e7d7099e643951aef692fbbd0437343b72c4371a648afb9429d8ac07240
Timestamp: 1734639598 Timestamp [UCT]: 2024-12-19 20:19:58 Age [y:d:h:m:s]: 00:095:13:07:48
Block: 1178836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68043 RingCT/type: yes/0
Extra: 01f2bc5e7d7099e643951aef692fbbd0437343b72c4371a648afb9429d8ac072400211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8388617f4d99de6849c84f9205003a7968fad59d3fe4e5e30c480f8a337340e 0.600000000000 1665225 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": 1178846, "vin": [ { "gen": { "height": 1178836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8388617f4d99de6849c84f9205003a7968fad59d3fe4e5e30c480f8a337340e" } } ], "extra": [ 1, 242, 188, 94, 125, 112, 153, 230, 67, 149, 26, 239, 105, 47, 187, 208, 67, 115, 67, 183, 44, 67, 113, 166, 72, 175, 185, 66, 157, 138, 192, 114, 64, 2, 17, 0, 0, 0, 9, 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