Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0a4d640c536768b7012e249955fc4f64b15c07fe000b6cb2726cfad6da9abbd

Tx prefix hash: 72a1cb9b09c088151d65fdc632f5073495e8936b691c86967ad61e6efbab88e1
Tx public key: 3c6b81ba6329dc787cbd5159d2206292d85e835c06140e4cdf88258a1b08aaa7
Timestamp: 1705225201 Timestamp [UCT]: 2024-01-14 09:40:01 Age [y:d:h:m:s]: 01:045:05:33:51
Block: 935051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293395 RingCT/type: yes/0
Extra: 013c6b81ba6329dc787cbd5159d2206292d85e835c06140e4cdf88258a1b08aaa70211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c267fcc2cdc99b6a107a5a2ea2d49955b2a71d56319d719a8bc7956f7c2f7f26 0.600000000000 1393067 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": 935061, "vin": [ { "gen": { "height": 935051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c267fcc2cdc99b6a107a5a2ea2d49955b2a71d56319d719a8bc7956f7c2f7f26" } } ], "extra": [ 1, 60, 107, 129, 186, 99, 41, 220, 120, 124, 189, 81, 89, 210, 32, 98, 146, 216, 94, 131, 92, 6, 20, 14, 76, 223, 136, 37, 138, 27, 8, 170, 167, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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