Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd5cf0e85e971482abbbba528701cbefd7d74d096e8dd78212b046d0ec102504

Tx prefix hash: 8da461b086e2ad3bebca5d15ff804ca5e5824b15747f5fb03a48a4a9954f6fd1
Tx public key: deb5c5f2b2e56282c2a215e10d211fee8562429f5cc4f990e05c3b75b04b5957
Timestamp: 1735397002 Timestamp [UCT]: 2024-12-28 14:43:22 Age [y:d:h:m:s]: 00:095:07:41:53
Block: 1185065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67915 RingCT/type: yes/0
Extra: 01deb5c5f2b2e56282c2a215e10d211fee8562429f5cc4f990e05c3b75b04b59570211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57d179320c17b9113cdd4a088e20c770891f63cc6c69768a1fa41aedb7d372ae 0.600000000000 1671530 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": 1185075, "vin": [ { "gen": { "height": 1185065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57d179320c17b9113cdd4a088e20c770891f63cc6c69768a1fa41aedb7d372ae" } } ], "extra": [ 1, 222, 181, 197, 242, 178, 229, 98, 130, 194, 162, 21, 225, 13, 33, 31, 238, 133, 98, 66, 159, 92, 196, 249, 144, 224, 92, 59, 117, 176, 75, 89, 87, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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