Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4f04505382768fc004d726b3f93129f5ab7da73929d7acc75c73991d52dcb49

Tx prefix hash: f52bc49e1088d9c3309429419d6e55fd1832e8b715c84a24fa246dfc507fb79d
Tx public key: ce8c9bdbe9358b0ef5664aceb751430c92793f1292d1e405877a6e296006b5ce
Timestamp: 1709923621 Timestamp [UCT]: 2024-03-08 18:47:01 Age [y:d:h:m:s]: 00:237:06:03:53
Block: 974028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169857 RingCT/type: yes/0
Extra: 01ce8c9bdbe9358b0ef5664aceb751430c92793f1292d1e405877a6e296006b5ce02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f20ad8f0da8bdfb9c05db11f5576b31b22acd27f6d058bcd5b268185fd70fe3e 0.600000000000 1433973 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": 974038, "vin": [ { "gen": { "height": 974028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f20ad8f0da8bdfb9c05db11f5576b31b22acd27f6d058bcd5b268185fd70fe3e" } } ], "extra": [ 1, 206, 140, 155, 219, 233, 53, 139, 14, 245, 102, 74, 206, 183, 81, 67, 12, 146, 121, 63, 18, 146, 209, 228, 5, 135, 122, 110, 41, 96, 6, 181, 206, 2, 17, 0, 0, 0, 2, 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