Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3e7bbfa57b3fda452975fda269417432c28d0fa0863f5659c009f9340b7d573

Tx prefix hash: 2640768f61a8809a0d4c285fbfa0d93fe890e3952b04c9a7a23a99585e435865
Tx public key: 4a879fdf71201a73c62c8ba324b64923cabd26fff42a2d602d4e0864d3145db3
Timestamp: 1745840665 Timestamp [UCT]: 2025-04-28 11:44:25 Age [y:d:h:m:s]: 00:255:05:43:17
Block: 1271278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180200 RingCT/type: yes/0
Extra: 014a879fdf71201a73c62c8ba324b64923cabd26fff42a2d602d4e0864d3145db30211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a138509af9a38e8d02bc3e0d8bcdf5ea8318d5c15aee2069e0045c8bc2cd1e3e 0.600000000000 1758535 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": 1271288, "vin": [ { "gen": { "height": 1271278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a138509af9a38e8d02bc3e0d8bcdf5ea8318d5c15aee2069e0045c8bc2cd1e3e" } } ], "extra": [ 1, 74, 135, 159, 223, 113, 32, 26, 115, 198, 44, 139, 163, 36, 182, 73, 35, 202, 189, 38, 255, 244, 42, 45, 96, 45, 78, 8, 100, 211, 20, 93, 179, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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