Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d854da4fdd183b374953edbb930fbc6b793ed4b86f2a7ba86be0f677b6978aa

Tx prefix hash: 8abe6498d0824b83b7687c9de8c93a9712c28d662031e2a53e697c776fba63e2
Tx public key: c209a48c45a18684631313e53f7d82682bfe7d6929a1e81411b41a79a40a8a04
Timestamp: 1725814517 Timestamp [UCT]: 2024-09-08 16:55:17 Age [y:d:h:m:s]: 00:204:12:04:37
Block: 1105763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145992 RingCT/type: yes/0
Extra: 01c209a48c45a18684631313e53f7d82682bfe7d6929a1e81411b41a79a40a8a0402110000000ae914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: d61b757a8e12d9c55b8a0c2ff3f49fa4d5d8eb948e20984d7aa37e753479add4 0.608000000000 1583212 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": 1105773, "vin": [ { "gen": { "height": 1105763 } } ], "vout": [ { "amount": 608000000, "target": { "key": "d61b757a8e12d9c55b8a0c2ff3f49fa4d5d8eb948e20984d7aa37e753479add4" } } ], "extra": [ 1, 194, 9, 164, 140, 69, 161, 134, 132, 99, 19, 19, 229, 63, 125, 130, 104, 43, 254, 125, 105, 41, 161, 232, 20, 17, 180, 26, 121, 164, 10, 138, 4, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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