Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9415122d9936a259447f9c079766340b5a16d4c0c3e3802bb8e9d981823891df

Tx prefix hash: f58bc69999afcabf8435ec635cc8cb432c9b35a8d8e6e0017583eea2b09b7cde
Tx public key: d3a3403e1576274294b6ed6d177e51a60c49cb27bd239b3a47240b502494089d
Timestamp: 1675318431 Timestamp [UCT]: 2023-02-02 06:13:51 Age [y:d:h:m:s]: 02:279:05:56:33
Block: 687997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 718925 RingCT/type: yes/0
Extra: 01d3a3403e1576274294b6ed6d177e51a60c49cb27bd239b3a47240b502494089d0211000000015029cbac000000000000000000

1 output(s) for total of 3.223890398000 dcy

stealth address amount amount idx
00: 0fff59b2abd9b0afa0f0317cd0f829990c1126116c9e5d4897b97d5f6a5cc647 3.223890398000 1130592 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": 688007, "vin": [ { "gen": { "height": 687997 } } ], "vout": [ { "amount": 3223890398, "target": { "key": "0fff59b2abd9b0afa0f0317cd0f829990c1126116c9e5d4897b97d5f6a5cc647" } } ], "extra": [ 1, 211, 163, 64, 62, 21, 118, 39, 66, 148, 182, 237, 109, 23, 126, 81, 166, 12, 73, 203, 39, 189, 35, 155, 58, 71, 36, 11, 80, 36, 148, 8, 157, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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