Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 415e2efddf38dbe2d9382f6a2f77d262984e62217377c2563a7de7d5636ed422

Tx prefix hash: 417d339d0daa0482f81bbea4632b0aaa3035cd6643a9b786c7ca9f2e8156774d
Tx public key: 6e3dbec6ade94b048f5e9869686dc276035692b74678e94268133aec2a13b11d
Timestamp: 1763102343 Timestamp [UCT]: 2025-11-14 06:39:03 Age [y:d:h:m:s]: 00:038:19:55:26
Block: 1411774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27803 RingCT/type: yes/0
Extra: 016e3dbec6ade94b048f5e9869686dc276035692b74678e94268133aec2a13b11d021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b3a79744052196f01e9f4f0f6f0a4fbef85625c37d1cf32631751cb30bd12fe 0.600000000000 1900237 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": 1411784, "vin": [ { "gen": { "height": 1411774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b3a79744052196f01e9f4f0f6f0a4fbef85625c37d1cf32631751cb30bd12fe" } } ], "extra": [ 1, 110, 61, 190, 198, 173, 233, 75, 4, 143, 94, 152, 105, 104, 109, 194, 118, 3, 86, 146, 183, 70, 120, 233, 66, 104, 19, 58, 236, 42, 19, 177, 29, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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