Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d42b50770249809c900c0a2aa01a3a26c1fc68e0465e0d947ef9a30ccac8821b

Tx prefix hash: d32dc2fcc1cb997af89629dbc89eb32a9f0da5e230afacf4fb3a556b50e53484
Tx public key: ee29531a1692a35723b872e7a3ff4e35af173084cab969ed71dd39e741cd0a9d
Timestamp: 1694303952 Timestamp [UCT]: 2023-09-09 23:59:12 Age [y:d:h:m:s]: 01:106:12:54:25
Block: 844706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337465 RingCT/type: yes/0
Extra: 01ee29531a1692a35723b872e7a3ff4e35af173084cab969ed71dd39e741cd0a9d021100000005faf35c9c000000000000000000

1 output(s) for total of 0.975300467000 dcy

stealth address amount amount idx
00: 5243946162863779f5ee113fe89c3ce36edf50fee8eb238531425ebf04e7c4fa 0.975300467000 1298032 of 0

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": 844716, "vin": [ { "gen": { "height": 844706 } } ], "vout": [ { "amount": 975300467, "target": { "key": "5243946162863779f5ee113fe89c3ce36edf50fee8eb238531425ebf04e7c4fa" } } ], "extra": [ 1, 238, 41, 83, 26, 22, 146, 163, 87, 35, 184, 114, 231, 163, 255, 78, 53, 175, 23, 48, 132, 202, 185, 105, 237, 113, 221, 57, 231, 65, 205, 10, 157, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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