Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb47a14f1652fa4a7234a3199152ddbcbe72ee69efb6ebe8dbeeaaf3be8772ca

Tx prefix hash: b6c3f7083ca902345c7cc658dcf13d8b8b4fd3a558420c31d83ac92703f67cf8
Tx public key: 926a3f12941142d4deadb3231065e598ad764a23e48d4b96f18d8f553a65f2c0
Timestamp: 1577799579 Timestamp [UCT]: 2019-12-31 13:39:39 Age [y:d:h:m:s]: 06:027:05:41:42
Block: 35804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1427714 RingCT/type: yes/0
Extra: 01926a3f12941142d4deadb3231065e598ad764a23e48d4b96f18d8f553a65f2c002110000000c8a2ee0d9000000000000000000

1 output(s) for total of 467.054261293000 dcy

stealth address amount amount idx
00: dd1d88824358d73de51f3a4a5d8df12ba22503db543166090d7d1c5f79dcc5c6 467.054261293000 60442 of 0

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": 35814, "vin": [ { "gen": { "height": 35804 } } ], "vout": [ { "amount": 467054261293, "target": { "key": "dd1d88824358d73de51f3a4a5d8df12ba22503db543166090d7d1c5f79dcc5c6" } } ], "extra": [ 1, 146, 106, 63, 18, 148, 17, 66, 212, 222, 173, 179, 35, 16, 101, 229, 152, 173, 118, 74, 35, 228, 141, 75, 150, 241, 141, 143, 85, 58, 101, 242, 192, 2, 17, 0, 0, 0, 12, 138, 46, 224, 217, 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