Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8483ca232de08850fbf1b3393f03160b6fde03b31d537403d6656650be0a23a

Tx prefix hash: c46bcde712d125e8dae3156846fd7a5727e1f00891981f6b1c802b67696ead71
Tx public key: 1816cb5f6ee125e69ef63d2665c6afa484ee096822f4aee0047d9a8da895785d
Timestamp: 1732451931 Timestamp [UCT]: 2024-11-24 12:38:51 Age [y:d:h:m:s]: 00:137:00:07:27
Block: 1160691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97731 RingCT/type: yes/0
Extra: 011816cb5f6ee125e69ef63d2665c6afa484ee096822f4aee0047d9a8da895785d0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c9d2d53df5e0bf9f12a87b4a19e4d5d59cdc23e761aa10dd1f89a1edbe4d9b7 0.600000000000 1646340 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": 1160701, "vin": [ { "gen": { "height": 1160691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c9d2d53df5e0bf9f12a87b4a19e4d5d59cdc23e761aa10dd1f89a1edbe4d9b7" } } ], "extra": [ 1, 24, 22, 203, 95, 110, 225, 37, 230, 158, 246, 61, 38, 101, 198, 175, 164, 132, 238, 9, 104, 34, 244, 174, 224, 4, 125, 154, 141, 168, 149, 120, 93, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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