Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1bcc894516512902237a6009ad2abc59e318a2a00b2fe1ab8d353b37190e2bd

Tx prefix hash: b5b9b8c9f8c1b88f8f3998590d95d00a9688cbc06b48820a434bd0ee1a22983b
Tx public key: 9f6a5d06f2bba3378ae5ff8c71f24c5d633a5fa8b621e1d56e53e3554d0b2fcf
Timestamp: 1745278327 Timestamp [UCT]: 2025-04-21 23:32:07 Age [y:d:h:m:s]: 00:214:00:54:34
Block: 1266609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150698 RingCT/type: yes/0
Extra: 019f6a5d06f2bba3378ae5ff8c71f24c5d633a5fa8b621e1d56e53e3554d0b2fcf0211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea08802c5c807197053ce075fb134e9fdceab75d3d32c4dd3bf71eb46eaf2fe4 0.600000000000 1753830 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": 1266619, "vin": [ { "gen": { "height": 1266609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea08802c5c807197053ce075fb134e9fdceab75d3d32c4dd3bf71eb46eaf2fe4" } } ], "extra": [ 1, 159, 106, 93, 6, 242, 187, 163, 55, 138, 229, 255, 140, 113, 242, 76, 93, 99, 58, 95, 168, 182, 33, 225, 213, 110, 83, 227, 85, 77, 11, 47, 207, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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