Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc18cfc0c6bc16edbaa355afd9e0dce63593bfca075797e7c2854b861db023e0

Tx prefix hash: f068ba19cee445663400600ec40d7eafbf56d6aef523d0f003b018b159831d3d
Tx public key: b59fdac6afe56e8b8f57c1351d21bab548f77ee8769795434a4072e2d984fb4e
Timestamp: 1738048795 Timestamp [UCT]: 2025-01-28 07:19:55 Age [y:d:h:m:s]: 00:346:07:50:32
Block: 1206782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245343 RingCT/type: yes/0
Extra: 01b59fdac6afe56e8b8f57c1351d21bab548f77ee8769795434a4072e2d984fb4e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d00b28de812742fc61ca6716771ed939a2e9788d896d98fa4a1ae2b837b90e5f 0.600000000000 1693495 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": 1206792, "vin": [ { "gen": { "height": 1206782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d00b28de812742fc61ca6716771ed939a2e9788d896d98fa4a1ae2b837b90e5f" } } ], "extra": [ 1, 181, 159, 218, 198, 175, 229, 110, 139, 143, 87, 193, 53, 29, 33, 186, 181, 72, 247, 126, 232, 118, 151, 149, 67, 74, 64, 114, 226, 217, 132, 251, 78, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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