Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56eb29c025cdc2966899778971a23cf2d88b78cab57345b5c138b18fd80da894

Tx prefix hash: 9678802144de2b85bf015d70f02a809885961fdc312d7c5bb523a89cc91d67a8
Tx public key: 18d65380d8e0f0745b4de5839ab759434690c832265d0f9c2abcba5b1208b8d2
Timestamp: 1727419366 Timestamp [UCT]: 2024-09-27 06:42:46 Age [y:d:h:m:s]: 00:148:14:48:29
Block: 1119074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105976 RingCT/type: yes/0
Extra: 0118d65380d8e0f0745b4de5839ab759434690c832265d0f9c2abcba5b1208b8d2021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79e12a0945d01b6d85244305c1ae61e4c2bbe2ec5e02e9af2ccc6316f41083dd 0.600000000000 1600493 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": 1119084, "vin": [ { "gen": { "height": 1119074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79e12a0945d01b6d85244305c1ae61e4c2bbe2ec5e02e9af2ccc6316f41083dd" } } ], "extra": [ 1, 24, 214, 83, 128, 216, 224, 240, 116, 91, 77, 229, 131, 154, 183, 89, 67, 70, 144, 200, 50, 38, 93, 15, 156, 42, 188, 186, 91, 18, 8, 184, 210, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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