Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bc23292634fe67a486ac29c73ee2eebf8c86446614e579dbd0eb2fb0ac4a176

Tx prefix hash: ee54d61f6d8704d34fb26aaa3cb994422bb5ba9d4f256dacb33e15302b356923
Tx public key: 72580d0ebbc43cb4c40b07663f1a6d1a4bb25d6ca0f9efb19ca99f4f8499f7e4
Timestamp: 1700914686 Timestamp [UCT]: 2023-11-25 12:18:06 Age [y:d:h:m:s]: 01:204:06:44:44
Block: 899333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407093 RingCT/type: yes/0
Extra: 0172580d0ebbc43cb4c40b07663f1a6d1a4bb25d6ca0f9efb19ca99f4f8499f7e4021100000003faf35c9c000000000000000000

1 output(s) for total of 0.642889636000 dcy

stealth address amount amount idx
00: 34209c0c5cf3fb00a4ce446b578f58f8142e4bf349c19ef9afcaf3cd916a4694 0.642889636000 1355782 of 0

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": 899343, "vin": [ { "gen": { "height": 899333 } } ], "vout": [ { "amount": 642889636, "target": { "key": "34209c0c5cf3fb00a4ce446b578f58f8142e4bf349c19ef9afcaf3cd916a4694" } } ], "extra": [ 1, 114, 88, 13, 14, 187, 196, 60, 180, 196, 11, 7, 102, 63, 26, 109, 26, 75, 178, 93, 108, 160, 249, 239, 177, 156, 169, 159, 79, 132, 153, 247, 228, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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