Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28955ff15b7fac02ff72f17606c845b71899bdd5fdb31add83b01e1947adde09

Tx prefix hash: 3743a13664e5a73b8f44d519408079d5dc9db3c7e0f4d894c55b4d526fd3ed99
Tx public key: 64f87f2eaf56c53f6b8553a20466cb4dc3184c86764d7cfbbb8b581a19dc0c91
Timestamp: 1721595681 Timestamp [UCT]: 2024-07-21 21:01:21 Age [y:d:h:m:s]: 00:307:06:44:30
Block: 1070769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219585 RingCT/type: yes/0
Extra: 0164f87f2eaf56c53f6b8553a20466cb4dc3184c86764d7cfbbb8b581a19dc0c9102110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0d6978ecf0ae991b410b35254d3e5b57de6e2c3207687c90b3cbbb7ced0ec88 0.600000000000 1542742 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": 1070779, "vin": [ { "gen": { "height": 1070769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0d6978ecf0ae991b410b35254d3e5b57de6e2c3207687c90b3cbbb7ced0ec88" } } ], "extra": [ 1, 100, 248, 127, 46, 175, 86, 197, 63, 107, 133, 83, 162, 4, 102, 203, 77, 195, 24, 76, 134, 118, 77, 124, 251, 187, 139, 88, 26, 25, 220, 12, 145, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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