Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4828774a63ca10e587d393c9c62576ebb79f6649604559be4f0295aa0893010

Tx prefix hash: 999c48be598809baf0285855a5ac5dc4c125c5bd3f93c04df95a6bc07b1ed6b1
Tx public key: 4965e885d719619b2cd03a1b191bea0fe191f36fae185c3cb0ee708b92baa4eb
Timestamp: 1720600788 Timestamp [UCT]: 2024-07-10 08:39:48 Age [y:d:h:m:s]: 00:264:20:51:32
Block: 1062544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189224 RingCT/type: yes/0
Extra: 014965e885d719619b2cd03a1b191bea0fe191f36fae185c3cb0ee708b92baa4eb02110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab497d82ff3ccd7aa8e88c4b2b9fe916109b48a004aed79ab575b630c8f2a79b 0.600000000000 1533049 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": 1062554, "vin": [ { "gen": { "height": 1062544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab497d82ff3ccd7aa8e88c4b2b9fe916109b48a004aed79ab575b630c8f2a79b" } } ], "extra": [ 1, 73, 101, 232, 133, 215, 25, 97, 155, 44, 208, 58, 27, 25, 27, 234, 15, 225, 145, 243, 111, 174, 24, 92, 60, 176, 238, 112, 139, 146, 186, 164, 235, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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