Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80e2b603dd85ccb798f5a5f31babc2c8a8c19a6130c0535faa4ecce53491b42c

Tx prefix hash: 3c1201c83206881c2a2eab1f68deea4a17e3000de698efc4f0b9a26c5ded2c5c
Tx public key: 18519bfb0bef6de6275c22cf5042fd2c090018b915da2177a116c03d4121c4f4
Timestamp: 1711548189 Timestamp [UCT]: 2024-03-27 14:03:09 Age [y:d:h:m:s]: 01:028:01:12:42
Block: 987510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281004 RingCT/type: yes/0
Extra: 0118519bfb0bef6de6275c22cf5042fd2c090018b915da2177a116c03d4121c4f402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef431a70f5ca0ecb1b618235ed9a4e1f6e845e5d2330156b4324c0247775beec 0.600000000000 1447761 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": 987520, "vin": [ { "gen": { "height": 987510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef431a70f5ca0ecb1b618235ed9a4e1f6e845e5d2330156b4324c0247775beec" } } ], "extra": [ 1, 24, 81, 155, 251, 11, 239, 109, 230, 39, 92, 34, 207, 80, 66, 253, 44, 9, 0, 24, 185, 21, 218, 33, 119, 161, 22, 192, 61, 65, 33, 196, 244, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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