Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 971fa20066b6ae036bacc5989b322a1deaea28dbc6749a08430ce872a88da1a3

Tx prefix hash: ca631b6154952d0387c203251f0e8447c8ed35b9e96dafe277ecc997941115d0
Tx public key: b5f5df2ca95eb211eba8f354c22fec525a908bb4bbf2b596edf031e66af1a121
Timestamp: 1748018643 Timestamp [UCT]: 2025-05-23 16:44:03 Age [y:d:h:m:s]: 00:181:21:25:23
Block: 1289311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127684 RingCT/type: yes/0
Extra: 01b5f5df2ca95eb211eba8f354c22fec525a908bb4bbf2b596edf031e66af1a1210211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 573fdb3e34e3a7b238eb1261ba8a320ee3b7d17c4c30826e5df6ef15cb6772cb 0.600000000000 1776778 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": 1289321, "vin": [ { "gen": { "height": 1289311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "573fdb3e34e3a7b238eb1261ba8a320ee3b7d17c4c30826e5df6ef15cb6772cb" } } ], "extra": [ 1, 181, 245, 223, 44, 169, 94, 178, 17, 235, 168, 243, 84, 194, 47, 236, 82, 90, 144, 139, 180, 187, 242, 181, 150, 237, 240, 49, 230, 106, 241, 161, 33, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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