Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efdb65bc46506f82714d1b53ffa04432c9623412e702a2b5077682bf4f974b3e

Tx prefix hash: 616bb735790574a0819d533756f39b95971c2b065fa3af9da2b482a8e1649756
Tx public key: 0d3d5348ec92908a60fb733024e228c91678b41e56b273ed8fbc2a460fd8f7b9
Timestamp: 1709947501 Timestamp [UCT]: 2024-03-09 01:25:01 Age [y:d:h:m:s]: 01:013:05:37:43
Block: 974222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270445 RingCT/type: yes/0
Extra: 010d3d5348ec92908a60fb733024e228c91678b41e56b273ed8fbc2a460fd8f7b902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a65367616ec2f9261fa706548cc39f46b36b7781ed8d849f7ff95953ecd9c3d7 0.600000000000 1434177 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": 974232, "vin": [ { "gen": { "height": 974222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a65367616ec2f9261fa706548cc39f46b36b7781ed8d849f7ff95953ecd9c3d7" } } ], "extra": [ 1, 13, 61, 83, 72, 236, 146, 144, 138, 96, 251, 115, 48, 36, 226, 40, 201, 22, 120, 180, 30, 86, 178, 115, 237, 143, 188, 42, 70, 15, 216, 247, 185, 2, 17, 0, 0, 0, 1, 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