Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54ea4e83919480186737c4c8c0df7152dc5def4aa0d35e4f44c492c08d985d63

Tx prefix hash: 4be038528d2a228d4d3b3e20fbb128f33c359f1d83f8ed5f85a379691723e0f6
Tx public key: 713a9013f0a63341179486aff1c3d98511dd0b62835f80de367cb660fd8321ed
Timestamp: 1583440969 Timestamp [UCT]: 2020-03-05 20:42:49 Age [y:d:h:m:s]: 04:298:07:13:00
Block: 76807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107938 RingCT/type: yes/0
Extra: 01713a9013f0a63341179486aff1c3d98511dd0b62835f80de367cb660fd8321ed0211000000064ac5aa02000000000000000000

1 output(s) for total of 341.591707764000 dcy

stealth address amount amount idx
00: 12937e11049d229fa7ce6b0bb3d906eeb3f6f47d60a411f7044ab9690e64b3dd 341.591707764000 141432 of 0

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": 76817, "vin": [ { "gen": { "height": 76807 } } ], "vout": [ { "amount": 341591707764, "target": { "key": "12937e11049d229fa7ce6b0bb3d906eeb3f6f47d60a411f7044ab9690e64b3dd" } } ], "extra": [ 1, 113, 58, 144, 19, 240, 166, 51, 65, 23, 148, 134, 175, 241, 195, 217, 133, 17, 221, 11, 98, 131, 95, 128, 222, 54, 124, 182, 96, 253, 131, 33, 237, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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