Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 366e210a961a697e5b2bb2361ffdc61314a0b75ac64df78bcf12ff9bd3dd9b19

Tx prefix hash: 6b956dc17130eba2c17569076db378639cf0a9da52f0c8eabe98374709a3e97c
Tx public key: c8b3ce29d46c9d39d349081ae9aa4cd23ecad43850608b933f773f0a5981493c
Timestamp: 1730676348 Timestamp [UCT]: 2024-11-03 23:25:48 Age [y:d:h:m:s]: 00:055:18:51:20
Block: 1145985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39904 RingCT/type: yes/0
Extra: 01c8b3ce29d46c9d39d349081ae9aa4cd23ecad43850608b933f773f0a5981493c021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed55562639f3fbb5f0238c070cf19379cfb5aff79c3f246bc4af3cc18f33d04d 0.600000000000 1630526 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": 1145995, "vin": [ { "gen": { "height": 1145985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed55562639f3fbb5f0238c070cf19379cfb5aff79c3f246bc4af3cc18f33d04d" } } ], "extra": [ 1, 200, 179, 206, 41, 212, 108, 157, 57, 211, 73, 8, 26, 233, 170, 76, 210, 62, 202, 212, 56, 80, 96, 139, 147, 63, 119, 63, 10, 89, 129, 73, 60, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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