Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ac6530030f71a8dc1372b6c875c6e0176a34f5f9112ff67fc02c15f4fca1c33

Tx prefix hash: 9e9afb32fba2fa4796cfd128b56ee8967863b4e8dacc41a07076d7373f692307
Tx public key: f4088da35d8e1f916be9abe523b13bb033efb5aeeb7df540f849f95d4223f64f
Timestamp: 1726968388 Timestamp [UCT]: 2024-09-22 01:26:28 Age [y:d:h:m:s]: 00:155:01:43:44
Block: 1115329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110609 RingCT/type: yes/0
Extra: 01f4088da35d8e1f916be9abe523b13bb033efb5aeeb7df540f849f95d4223f64f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa0e5db174edf324acc2b2f578634e278960fa0fba72fe872c9093eb75ecaef7 0.600000000000 1595424 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": 1115339, "vin": [ { "gen": { "height": 1115329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa0e5db174edf324acc2b2f578634e278960fa0fba72fe872c9093eb75ecaef7" } } ], "extra": [ 1, 244, 8, 141, 163, 93, 142, 31, 145, 107, 233, 171, 229, 35, 177, 59, 176, 51, 239, 181, 174, 235, 125, 245, 64, 248, 73, 249, 93, 66, 35, 246, 79, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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