Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dccdf7eb4a4fbeda1f488eb876c599fcfb6e6e205f6cf9680fe9785ee9ac5bb8

Tx prefix hash: 974d2efd93c354178ed9a739891cdbc825f9f7223773f6592edbb9e49dfbe28d
Tx public key: 9d12bc6d5cbb338b696d1a3fcc8bc4b1c97774449bfe052e5cbe390743ffae8b
Timestamp: 1703684633 Timestamp [UCT]: 2023-12-27 13:43:53 Age [y:d:h:m:s]: 01:062:16:28:29
Block: 922295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305877 RingCT/type: yes/0
Extra: 019d12bc6d5cbb338b696d1a3fcc8bc4b1c97774449bfe052e5cbe390743ffae8b02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29e7594c7ad747ad84b430f377b915c4d50e147aa69bd21db8639fb84ce056e6 0.600000000000 1379991 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": 922305, "vin": [ { "gen": { "height": 922295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29e7594c7ad747ad84b430f377b915c4d50e147aa69bd21db8639fb84ce056e6" } } ], "extra": [ 1, 157, 18, 188, 109, 92, 187, 51, 139, 105, 109, 26, 63, 204, 139, 196, 177, 201, 119, 116, 68, 155, 254, 5, 46, 92, 190, 57, 7, 67, 255, 174, 139, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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