Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 569c66d8ce5e7183ca79e39c8921f20941802239154ed1921d8f75729fd3ea95

Tx prefix hash: adad07aa4875ad96570150dbb3fca41350dd0173f63b0caeccf684473b9b29b2
Tx public key: fc74b756f8e49d5d19233ae7f4841f22c0088e2e0f66790eff0e131dc730333a
Timestamp: 1685431698 Timestamp [UCT]: 2023-05-30 07:28:18 Age [y:d:h:m:s]: 02:164:12:11:02
Block: 771216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 637367 RingCT/type: yes/0
Extra: 01fc74b756f8e49d5d19233ae7f4841f22c0088e2e0f66790eff0e131dc730333a02110000000833af99f4000000000000000000

1 output(s) for total of 1.708603993000 dcy

stealth address amount amount idx
00: 703622785c557cb8a674be8eca414f692b1548e18d8bd7f8f6dbbfcf8b3fce54 1.708603993000 1220565 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": 771226, "vin": [ { "gen": { "height": 771216 } } ], "vout": [ { "amount": 1708603993, "target": { "key": "703622785c557cb8a674be8eca414f692b1548e18d8bd7f8f6dbbfcf8b3fce54" } } ], "extra": [ 1, 252, 116, 183, 86, 248, 228, 157, 93, 25, 35, 58, 231, 244, 132, 31, 34, 192, 8, 142, 46, 15, 102, 121, 14, 255, 14, 19, 29, 199, 48, 51, 58, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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