Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abf5b7867d96d2b982983a56deb373242cb8e3de8a0ed54942634f0fd04be8d6

Tx prefix hash: 63808cb777cb39db5621a7d00897f0bfb48fa39fe905edbe978ab6d109806113
Tx public key: d1f2bb3d7a51ec48219c902e6aff450f6166a6476d7d3408d7a91841ac6ea978
Timestamp: 1727219118 Timestamp [UCT]: 2024-09-24 23:05:18 Age [y:d:h:m:s]: 00:232:04:50:50
Block: 1117399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165798 RingCT/type: yes/0
Extra: 01d1f2bb3d7a51ec48219c902e6aff450f6166a6476d7d3408d7a91841ac6ea978021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 494c7ecb44f9d664c3725256c7459714616fc6f4a67b30bb305e44d2de644183 0.600000000000 1598226 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": 1117409, "vin": [ { "gen": { "height": 1117399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "494c7ecb44f9d664c3725256c7459714616fc6f4a67b30bb305e44d2de644183" } } ], "extra": [ 1, 209, 242, 187, 61, 122, 81, 236, 72, 33, 156, 144, 46, 106, 255, 69, 15, 97, 102, 166, 71, 109, 125, 52, 8, 215, 169, 24, 65, 172, 110, 169, 120, 2, 17, 0, 0, 0, 6, 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