Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f6e99361e77b9dc2db24628a7e7cb6ce4e042501c92d38add96314ad5a826a9

Tx prefix hash: 297555c4144c6ff212944af215e7bad976257e8214e03cdc36e5b9b88711c39c
Tx public key: dfd6407e84f3a2f16973feaa7a39fe37f845cd918159b854377e6046af0abaab
Timestamp: 1675406716 Timestamp [UCT]: 2023-02-03 06:45:16 Age [y:d:h:m:s]: 02:086:21:16:06
Block: 688734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 583743 RingCT/type: yes/0
Extra: 01dfd6407e84f3a2f16973feaa7a39fe37f845cd918159b854377e6046af0abaab0211000000037e406890000000000000000000

1 output(s) for total of 3.205813701000 dcy

stealth address amount amount idx
00: 79cbf712ace177248eaa1b6e9efe391de1d2e4cb686e3fbe02edb9571ca82535 3.205813701000 1131368 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": 688744, "vin": [ { "gen": { "height": 688734 } } ], "vout": [ { "amount": 3205813701, "target": { "key": "79cbf712ace177248eaa1b6e9efe391de1d2e4cb686e3fbe02edb9571ca82535" } } ], "extra": [ 1, 223, 214, 64, 126, 132, 243, 162, 241, 105, 115, 254, 170, 122, 57, 254, 55, 248, 69, 205, 145, 129, 89, 184, 84, 55, 126, 96, 70, 175, 10, 186, 171, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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