Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e96cd5742e9666711b72d834f7b007c382e3ac7fd93c663e9d194aa1d060825

Tx prefix hash: 73f55ed399bae3f0a2efb2589fc5ef337837acae4d75941d191b502c1d7ce11a
Tx public key: b7d1eaaee6a7eb08cf837a32f02b3fd78529d5438b3020a1e5eeb0520ca1ba5b
Timestamp: 1734408765 Timestamp [UCT]: 2024-12-17 04:12:45 Age [y:d:h:m:s]: 00:092:21:54:41
Block: 1176922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66187 RingCT/type: yes/0
Extra: 01b7d1eaaee6a7eb08cf837a32f02b3fd78529d5438b3020a1e5eeb0520ca1ba5b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf20946a3e44e85a75a0b2eb1636371ae78e91f2ec47afa86f51f50be1191b41 0.600000000000 1663283 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": 1176932, "vin": [ { "gen": { "height": 1176922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf20946a3e44e85a75a0b2eb1636371ae78e91f2ec47afa86f51f50be1191b41" } } ], "extra": [ 1, 183, 209, 234, 174, 230, 167, 235, 8, 207, 131, 122, 50, 240, 43, 63, 215, 133, 41, 213, 67, 139, 48, 32, 161, 229, 238, 176, 82, 12, 161, 186, 91, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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