Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee4e28748c12aadb7c5246630e04527e434ea66a75c1551d7910d303dfefa1f0

Tx prefix hash: 0c4d44af7ff12db99c1d910ab9adfa65b902bb49a2a43a6c8bdb6b1f708020b6
Tx public key: 3379522e10b3c8b9d403561feff113f17026fe32e83fdcf57b110ada9c5ad6a9
Timestamp: 1729305820 Timestamp [UCT]: 2024-10-19 02:43:40 Age [y:d:h:m:s]: 00:003:20:34:03
Block: 1134698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2740 RingCT/type: yes/0
Extra: 013379522e10b3c8b9d403561feff113f17026fe32e83fdcf57b110ada9c5ad6a90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b00aa163d1e2b0cf693b62111d2eb48e9a57d712eb6cba0205634823955f066 0.600000000000 1618023 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": 1134708, "vin": [ { "gen": { "height": 1134698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b00aa163d1e2b0cf693b62111d2eb48e9a57d712eb6cba0205634823955f066" } } ], "extra": [ 1, 51, 121, 82, 46, 16, 179, 200, 185, 212, 3, 86, 31, 239, 241, 19, 241, 112, 38, 254, 50, 232, 63, 220, 245, 123, 17, 10, 218, 156, 90, 214, 169, 2, 17, 0, 0, 0, 4, 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