Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a070141c3a29925e24c7d5fa6634e9a0ef2e04a927e0c50c48cc44c4557da1d5

Tx prefix hash: 1f31749f0ec30d2f035fac6e7f1aaf1543c880112e985cc74f62def0f78bf753
Tx public key: 637fd2cf5817a864cc13efe95bbab387e3d92dd2be2ed72e4998e6bfb93b6710
Timestamp: 1749609101 Timestamp [UCT]: 2025-06-11 02:31:41 Age [y:d:h:m:s]: 00:152:11:32:49
Block: 1302456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106670 RingCT/type: yes/0
Extra: 01637fd2cf5817a864cc13efe95bbab387e3d92dd2be2ed72e4998e6bfb93b6710021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f13c5c485ff4ddb6b3f9fcdff18a797152788fe4d313ea09492bb4d0953fd048 0.600000000000 1790027 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": 1302466, "vin": [ { "gen": { "height": 1302456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f13c5c485ff4ddb6b3f9fcdff18a797152788fe4d313ea09492bb4d0953fd048" } } ], "extra": [ 1, 99, 127, 210, 207, 88, 23, 168, 100, 204, 19, 239, 233, 91, 186, 179, 135, 227, 217, 45, 210, 190, 46, 215, 46, 73, 152, 230, 191, 185, 59, 103, 16, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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