Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ac9f0ff2a4181cc7125def51e477ec7312496c0a738d6abe522f3c73766d008

Tx prefix hash: 10a1c26eb4631a12616a8cda22f9de7e2b50a8e8c3664d7b1753481c451a9a3f
Tx public key: 264d2721df364e6d4d4b683118308c13d0fda9bc19ecd6441e7d16dc2dba6bcd
Timestamp: 1745625114 Timestamp [UCT]: 2025-04-25 23:51:54 Age [y:d:h:m:s]: 00:012:04:28:07
Block: 1269462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8735 RingCT/type: yes/0
Extra: 01264d2721df364e6d4d4b683118308c13d0fda9bc19ecd6441e7d16dc2dba6bcd0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1e18166dd3ffe6195fedcafb0692cea34fc709ee2af3bad9c59c4847ed7edbe 0.600000000000 1756701 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": 1269472, "vin": [ { "gen": { "height": 1269462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1e18166dd3ffe6195fedcafb0692cea34fc709ee2af3bad9c59c4847ed7edbe" } } ], "extra": [ 1, 38, 77, 39, 33, 223, 54, 78, 109, 77, 75, 104, 49, 24, 48, 140, 19, 208, 253, 169, 188, 25, 236, 214, 68, 30, 125, 22, 220, 45, 186, 107, 205, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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