Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10230f0b0dea003e052caf2fbe1511efeaac3d98cbd810bf89037ae0bb4336eb

Tx prefix hash: 4691799017c58add384b39d6e041c1855e238451ffe9c3a4d737f0655d1d5b37
Tx public key: 1643999d22147319df043f2cc42ddb8f76b56a634bb1e5eb51b41aca9e769a7c
Timestamp: 1718731031 Timestamp [UCT]: 2024-06-18 17:17:11 Age [y:d:h:m:s]: 00:289:08:53:21
Block: 1047032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206775 RingCT/type: yes/0
Extra: 011643999d22147319df043f2cc42ddb8f76b56a634bb1e5eb51b41aca9e769a7c0211000000020bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74663b444957fb23b2a666328fb48ef1cb7ec84da7bbd47c117febb97f674c8f 0.600000000000 1516851 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": 1047042, "vin": [ { "gen": { "height": 1047032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74663b444957fb23b2a666328fb48ef1cb7ec84da7bbd47c117febb97f674c8f" } } ], "extra": [ 1, 22, 67, 153, 157, 34, 20, 115, 25, 223, 4, 63, 44, 196, 45, 219, 143, 118, 181, 106, 99, 75, 177, 229, 235, 81, 180, 26, 202, 158, 118, 154, 124, 2, 17, 0, 0, 0, 2, 11, 186, 22, 215, 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