Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de37d3bc972d45d49608f05a885863fe368d933fe24ce46ae23d3757284b796d

Tx prefix hash: a6eafa4747e255d27a85caf514059a33990d7041edf8b7ecb1be9acce596f85d
Tx public key: eb455b8ad8c17d0c4a8c14f2ff1bd1134278fa0fc60746a2656aafb9f4883865
Timestamp: 1711501373 Timestamp [UCT]: 2024-03-27 01:02:53 Age [y:d:h:m:s]: 01:237:04:51:44
Block: 987120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428206 RingCT/type: yes/0
Extra: 01eb455b8ad8c17d0c4a8c14f2ff1bd1134278fa0fc60746a2656aafb9f488386502110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e35c4179614dd7cde6d734003c8c28dc998237d5a1d73a7a031165a2e6c852c8 0.600000000000 1447361 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": 987130, "vin": [ { "gen": { "height": 987120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e35c4179614dd7cde6d734003c8c28dc998237d5a1d73a7a031165a2e6c852c8" } } ], "extra": [ 1, 235, 69, 91, 138, 216, 193, 125, 12, 74, 140, 20, 242, 255, 27, 209, 19, 66, 120, 250, 15, 198, 7, 70, 162, 101, 106, 175, 185, 244, 136, 56, 101, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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