Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bd7cc4ac9c3ffb3191fc83b50be61b23306a5fd3f1ab39750a72dfb752a73b2

Tx prefix hash: 72f6db32c994abf89e8bd4a1053c65b28dc5f7f9a39ed7d3e791905884c8af58
Tx public key: 4b86a9e1ef351a7542a7203521d7bb4983e2916dbcdcd88319da8066483b2dbe
Timestamp: 1705834884 Timestamp [UCT]: 2024-01-21 11:01:24 Age [y:d:h:m:s]: 01:124:11:20:08
Block: 940091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350101 RingCT/type: yes/0
Extra: 014b86a9e1ef351a7542a7203521d7bb4983e2916dbcdcd88319da8066483b2dbe0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6a329316ca4d0c1c40876066c8b14ed0e6bc526f34fc53e72598b4954d07cf6 0.600000000000 1398225 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": 940101, "vin": [ { "gen": { "height": 940091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6a329316ca4d0c1c40876066c8b14ed0e6bc526f34fc53e72598b4954d07cf6" } } ], "extra": [ 1, 75, 134, 169, 225, 239, 53, 26, 117, 66, 167, 32, 53, 33, 215, 187, 73, 131, 226, 145, 109, 188, 220, 216, 131, 25, 218, 128, 102, 72, 59, 45, 190, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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