Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60958d2ac3d4c0191556aa63f3238e8896cc0c711abbef5a46c4d52aaa52d86b

Tx prefix hash: 75588067e74ec6b0d76f1d9d5525bafbddd00283f5594e246e0c898ddd58a477
Tx public key: 3ec2ca9ddd678bc57e3fc29a4c6395a805e8fa2cdbcf05fc4b6e8ce1ea7d5324
Timestamp: 1703169117 Timestamp [UCT]: 2023-12-21 14:31:57 Age [y:d:h:m:s]: 01:332:07:33:28
Block: 918012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496362 RingCT/type: yes/0
Extra: 013ec2ca9ddd678bc57e3fc29a4c6395a805e8fa2cdbcf05fc4b6e8ce1ea7d53240211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8321557f2cf610c008d0cc1dbcc9ebebd5e32647969a416de5a10f24645d5a74 0.600000000000 1375648 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": 918022, "vin": [ { "gen": { "height": 918012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8321557f2cf610c008d0cc1dbcc9ebebd5e32647969a416de5a10f24645d5a74" } } ], "extra": [ 1, 62, 194, 202, 157, 221, 103, 139, 197, 126, 63, 194, 154, 76, 99, 149, 168, 5, 232, 250, 44, 219, 207, 5, 252, 75, 110, 140, 225, 234, 125, 83, 36, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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