Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47536f676c9487f576df85ec7b300eba5504b7e3a2b02de7482de3f6051c8231

Tx prefix hash: b0b2bda92cdce34da435b816d004505cb14c8623e398d9b9c91836e40d8f4048
Tx public key: 4cc52fbe1da8765ad3f99902d5fa2dfe17afd140b1cf16a8e53e0e0c159f076b
Timestamp: 1708178880 Timestamp [UCT]: 2024-02-17 14:08:00 Age [y:d:h:m:s]: 01:126:06:01:18
Block: 959547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351102 RingCT/type: yes/0
Extra: 014cc52fbe1da8765ad3f99902d5fa2dfe17afd140b1cf16a8e53e0e0c159f076b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af0a340ae469d50aa525c5ae69c77401b8262e96379f8a90dfb02e979a087219 0.600000000000 1419084 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": 959557, "vin": [ { "gen": { "height": 959547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af0a340ae469d50aa525c5ae69c77401b8262e96379f8a90dfb02e979a087219" } } ], "extra": [ 1, 76, 197, 47, 190, 29, 168, 118, 90, 211, 249, 153, 2, 213, 250, 45, 254, 23, 175, 209, 64, 177, 207, 22, 168, 229, 62, 14, 12, 21, 159, 7, 107, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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