Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76763e47d0cea7dedb4ae776db6ede179eb52ff4bd4ac8884f7880ced76da673

Tx prefix hash: d853727a9f19b70d669d800ee55f621b8ed71124a4da035e5943fe22502fbd32
Tx public key: ec8555e439c0a736811459b56fc3b27ca71e5b70f4c37d8f883a9fb3d0c27eea
Timestamp: 1711586302 Timestamp [UCT]: 2024-03-28 00:38:22 Age [y:d:h:m:s]: 01:021:14:18:30
Block: 987817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276400 RingCT/type: yes/0
Extra: 01ec8555e439c0a736811459b56fc3b27ca71e5b70f4c37d8f883a9fb3d0c27eea02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7f4509baceaf2b0ebd92d50f3e59c0033b548103bff2861cd6ea94a2d1bacf6 0.600000000000 1448076 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": 987827, "vin": [ { "gen": { "height": 987817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7f4509baceaf2b0ebd92d50f3e59c0033b548103bff2861cd6ea94a2d1bacf6" } } ], "extra": [ 1, 236, 133, 85, 228, 57, 192, 167, 54, 129, 20, 89, 181, 111, 195, 178, 124, 167, 30, 91, 112, 244, 195, 125, 143, 136, 58, 159, 179, 208, 194, 126, 234, 2, 17, 0, 0, 0, 6, 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