Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ee39147f642215502bee381561ddc4740ce9dc195d1e329d2b7c99acb451d67

Tx prefix hash: cbf0556884bd11c428b95bdab6b2d76baf992198b6eae12f9cb9209493d53370
Tx public key: 1335a3e9c2d4d70e602e861e6f586ef5bdef67b789bc20d0966b9c9d66d187f2
Timestamp: 1719107015 Timestamp [UCT]: 2024-06-23 01:43:35 Age [y:d:h:m:s]: 00:272:10:39:55
Block: 1050133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194695 RingCT/type: yes/0
Extra: 011335a3e9c2d4d70e602e861e6f586ef5bdef67b789bc20d0966b9c9d66d187f202110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e5290cbf59d57f68d56d9fad95a6f1756734726ff80b7ca958b47b9111ad232 0.600000000000 1520294 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": 1050143, "vin": [ { "gen": { "height": 1050133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e5290cbf59d57f68d56d9fad95a6f1756734726ff80b7ca958b47b9111ad232" } } ], "extra": [ 1, 19, 53, 163, 233, 194, 212, 215, 14, 96, 46, 134, 30, 111, 88, 110, 245, 189, 239, 103, 183, 137, 188, 32, 208, 150, 107, 156, 157, 102, 209, 135, 242, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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