Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7c91d309b093297859c82da0310ed6a0f8a459a73911cd30880083ab9449df7

Tx prefix hash: 4cce73e8cd5b7b3690ed60dc8f13a2e07a9462084a4ae489d105eb9cd09ea70e
Tx public key: fa3d90a7a52986f6332b937b4828dfc25b4c7a9a768c986d7a4006d8c55066d3
Timestamp: 1706290393 Timestamp [UCT]: 2024-01-26 17:33:13 Age [y:d:h:m:s]: 01:286:12:46:53
Block: 943868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463592 RingCT/type: yes/0
Extra: 01fa3d90a7a52986f6332b937b4828dfc25b4c7a9a768c986d7a4006d8c55066d30211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb7941a671145634493213b26e9fbc9500ec7e9393272e799d4889cf2fc9302d 0.600000000000 1402094 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": 943878, "vin": [ { "gen": { "height": 943868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb7941a671145634493213b26e9fbc9500ec7e9393272e799d4889cf2fc9302d" } } ], "extra": [ 1, 250, 61, 144, 167, 165, 41, 134, 246, 51, 43, 147, 123, 72, 40, 223, 194, 91, 76, 122, 154, 118, 140, 152, 109, 122, 64, 6, 216, 197, 80, 102, 211, 2, 17, 0, 0, 0, 8, 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