Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c0fcbb08fc74b9b48b8019f0bd20df902fba351280dcac17aeed9e61f3a284b

Tx prefix hash: 767188d29afe6245c6aa1545e86bf54b175d98319d845d5f4f55e4fa96530ad5
Tx public key: 621c1691593e90bbc9124c39f07c150dbad5cff1b743855f6c9c8b83a504dce3
Timestamp: 1738747599 Timestamp [UCT]: 2025-02-05 09:26:39 Age [y:d:h:m:s]: 00:282:14:41:52
Block: 1212548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199745 RingCT/type: yes/0
Extra: 01621c1691593e90bbc9124c39f07c150dbad5cff1b743855f6c9c8b83a504dce30211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9fde907f42071a28250a1a0a0b24a9dd4e2da5f26d2d1ea6ec5e7d8c4f4ca08 0.600000000000 1699321 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": 1212558, "vin": [ { "gen": { "height": 1212548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9fde907f42071a28250a1a0a0b24a9dd4e2da5f26d2d1ea6ec5e7d8c4f4ca08" } } ], "extra": [ 1, 98, 28, 22, 145, 89, 62, 144, 187, 201, 18, 76, 57, 240, 124, 21, 13, 186, 213, 207, 241, 183, 67, 133, 95, 108, 156, 139, 131, 165, 4, 220, 227, 2, 17, 0, 0, 0, 7, 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