Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9352e026b8bdb5600f8ef7726b208f5f9d792dfa6ddd7e11f577fade720c805b

Tx prefix hash: 6fe62b0f4ec54156c3ba6d49323cd40b31256f04f4748c9922aa87dba08c3eec
Tx public key: 69c320d660945ddf8de4a611fc9415cd80a99822969fa5f2cb5ce0a7c685d1c4
Timestamp: 1729027449 Timestamp [UCT]: 2024-10-15 21:24:09 Age [y:d:h:m:s]: 00:099:15:40:48
Block: 1132398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71187 RingCT/type: yes/0
Extra: 0169c320d660945ddf8de4a611fc9415cd80a99822969fa5f2cb5ce0a7c685d1c4021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8881d1b6d4f2efc065262ebf5a2f48a8d146c1160e25a4576a2a1ce73f501671 0.600000000000 1615311 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": 1132408, "vin": [ { "gen": { "height": 1132398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8881d1b6d4f2efc065262ebf5a2f48a8d146c1160e25a4576a2a1ce73f501671" } } ], "extra": [ 1, 105, 195, 32, 214, 96, 148, 93, 223, 141, 228, 166, 17, 252, 148, 21, 205, 128, 169, 152, 34, 150, 159, 165, 242, 203, 92, 224, 167, 198, 133, 209, 196, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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