Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e37d250a1679cfff6b4d65a7836ac80ddc8e6a5db10ed7527c9c87cd660bd139

Tx prefix hash: cc03f05fbfd41466f465e04e0ae4d5657ae4c309810c0285c54777ec56303994
Tx public key: 2c65a1a37cf05cf18a72c9c76061f19e0ea8e249d6c611f82d4567d61dd24e77
Timestamp: 1707033742 Timestamp [UCT]: 2024-02-04 08:02:22 Age [y:d:h:m:s]: 01:024:05:55:41
Block: 950048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278362 RingCT/type: yes/0
Extra: 012c65a1a37cf05cf18a72c9c76061f19e0ea8e249d6c611f82d4567d61dd24e7702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ca47384ffd82141fd272faada90d12d3449747f7d7dc005bb3ea5d42cd89060 0.600000000000 1408604 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": 950058, "vin": [ { "gen": { "height": 950048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ca47384ffd82141fd272faada90d12d3449747f7d7dc005bb3ea5d42cd89060" } } ], "extra": [ 1, 44, 101, 161, 163, 124, 240, 92, 241, 138, 114, 201, 199, 96, 97, 241, 158, 14, 168, 226, 73, 214, 198, 17, 248, 45, 69, 103, 214, 29, 210, 78, 119, 2, 17, 0, 0, 0, 3, 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