Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5e1cc6f6f9c77686b0572b02ebcbea16f959db2c3cf426feb31634b0a583207

Tx prefix hash: 875d9aceb89af334683e48786710f22cd1e8d4ed4d91f332956cf1a415472e26
Tx public key: 78327fc02776c1a2d07d5c075b0fcc8bdf6f48401ddcbdf335cd96f6ad918013
Timestamp: 1706469948 Timestamp [UCT]: 2024-01-28 19:25:48 Age [y:d:h:m:s]: 01:282:13:13:34
Block: 945360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460722 RingCT/type: yes/0
Extra: 0178327fc02776c1a2d07d5c075b0fcc8bdf6f48401ddcbdf335cd96f6ad9180130211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2a057f080d128072ebe75b8baaeb823453549cbd9ff4e26d163d9ea4cfeb7af 0.600000000000 1403672 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": 945370, "vin": [ { "gen": { "height": 945360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2a057f080d128072ebe75b8baaeb823453549cbd9ff4e26d163d9ea4cfeb7af" } } ], "extra": [ 1, 120, 50, 127, 192, 39, 118, 193, 162, 208, 125, 92, 7, 91, 15, 204, 139, 223, 111, 72, 64, 29, 220, 189, 243, 53, 205, 150, 246, 173, 145, 128, 19, 2, 17, 0, 0, 0, 1, 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