Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fd1fdeb7b5307b389e7dc40ea0110ba3aa61223c735ee2671fa9144131e8ac6

Tx prefix hash: 286b3e6ed7fe22dcb5f10863fa34860ef04c8ec5647ed1e833d8410bc96de4ea
Tx public key: e95ad9de46f4fb68249d8cfd491fedaa15a2c473008a063e8272702d03703d5c
Timestamp: 1752378681 Timestamp [UCT]: 2025-07-13 03:51:21 Age [y:d:h:m:s]: 00:163:22:31:37
Block: 1324344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115926 RingCT/type: yes/0
Extra: 01e95ad9de46f4fb68249d8cfd491fedaa15a2c473008a063e8272702d03703d5c0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6054e704b73f504f38fc1bd5580931b0866bb4e899d150be5fca4be273e875c3 0.600000000000 1812087 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": 1324354, "vin": [ { "gen": { "height": 1324344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6054e704b73f504f38fc1bd5580931b0866bb4e899d150be5fca4be273e875c3" } } ], "extra": [ 1, 233, 90, 217, 222, 70, 244, 251, 104, 36, 157, 140, 253, 73, 31, 237, 170, 21, 162, 196, 115, 0, 138, 6, 62, 130, 114, 112, 45, 3, 112, 61, 92, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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