Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fc5bb3d50fe66b6fc2fea9ea3d39631db0a8ae06af034d0b793125dcd589b07

Tx prefix hash: 17b3b70919f75f8cf9ed02c4fdab343bd3c14f8010ac3109e74e1a4002ab6b76
Tx public key: 498d29489be5827faf0836c0894cb1c9841678c88fc48ece8ce4750ce0f5dc91
Timestamp: 1711527446 Timestamp [UCT]: 2024-03-27 08:17:26 Age [y:d:h:m:s]: 00:270:10:04:24
Block: 987341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193582 RingCT/type: yes/0
Extra: 01498d29489be5827faf0836c0894cb1c9841678c88fc48ece8ce4750ce0f5dc910211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ecb84989bd5e919fc83c0d4b74adc08f76a147ae0ba32d0c5a7c27f4f9a6219 0.600000000000 1447588 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": 987351, "vin": [ { "gen": { "height": 987341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ecb84989bd5e919fc83c0d4b74adc08f76a147ae0ba32d0c5a7c27f4f9a6219" } } ], "extra": [ 1, 73, 141, 41, 72, 155, 229, 130, 127, 175, 8, 54, 192, 137, 76, 177, 201, 132, 22, 120, 200, 143, 196, 142, 206, 140, 228, 117, 12, 224, 245, 220, 145, 2, 17, 0, 0, 0, 2, 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