Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b66510b7d4836ae06638ffc07339da9886ee6b53ea266c406d445a20ac8167d

Tx prefix hash: c4f0791992dd0eb87ceb54822b3bf29dacbe309a4b950c789a60f5c0e31c63e4
Tx public key: dc1ebac2799da521cba8b1e56a4ed09a0154a6279ed65a7585918d3b5ddedd26
Timestamp: 1733504801 Timestamp [UCT]: 2024-12-06 17:06:41 Age [y:d:h:m:s]: 00:105:19:23:05
Block: 1169412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75419 RingCT/type: yes/0
Extra: 01dc1ebac2799da521cba8b1e56a4ed09a0154a6279ed65a7585918d3b5ddedd260211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d2352c9bbad8d0c5fe75a1ee1a05e161b40c88f07e8d2204fe5c8aac6820ad6 0.600000000000 1655129 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": 1169422, "vin": [ { "gen": { "height": 1169412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d2352c9bbad8d0c5fe75a1ee1a05e161b40c88f07e8d2204fe5c8aac6820ad6" } } ], "extra": [ 1, 220, 30, 186, 194, 121, 157, 165, 33, 203, 168, 177, 229, 106, 78, 208, 154, 1, 84, 166, 39, 158, 214, 90, 117, 133, 145, 141, 59, 93, 222, 221, 38, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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