Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8104d729900db5362ce2a0152e298831817efa9be9c88e206583005b0c9383ae

Tx prefix hash: f4312acb43370381f7e8c2e3f6b6894ba9480e2bfc137327bb4807833ad80329
Tx public key: 2f371ce60f908383036e62c9f7698ee4b8e0dac97c73434cf86da5d9a3138c79
Timestamp: 1696320566 Timestamp [UCT]: 2023-10-03 08:09:26 Age [y:d:h:m:s]: 01:102:15:46:40
Block: 861450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334620 RingCT/type: yes/0
Extra: 012f371ce60f908383036e62c9f7698ee4b8e0dac97c73434cf86da5d9a3138c7902110000000575e3f0e9000000000000000000

1 output(s) for total of 0.858338484000 dcy

stealth address amount amount idx
00: d6358d05bde78d4c8d4de499c60cdc8eaf4cfa25cbf5f23aded664a560a36ef0 0.858338484000 1315792 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": 861460, "vin": [ { "gen": { "height": 861450 } } ], "vout": [ { "amount": 858338484, "target": { "key": "d6358d05bde78d4c8d4de499c60cdc8eaf4cfa25cbf5f23aded664a560a36ef0" } } ], "extra": [ 1, 47, 55, 28, 230, 15, 144, 131, 131, 3, 110, 98, 201, 247, 105, 142, 228, 184, 224, 218, 201, 124, 115, 67, 76, 248, 109, 165, 217, 163, 19, 140, 121, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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