Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4094d082e04a31202c44bfbe641ecd0b5cf5b1f5a96a0c4589eb17a966b772b8

Tx prefix hash: 37d30dfbd50b30a9797bc30b1a2d1db0af126432d016d4e2ebd7d3cf3a398946
Tx public key: a4f97fdaf9d66ad5d8d720ef259a2b29efbd87adc667400ba3b16af92231ee3d
Timestamp: 1748540929 Timestamp [UCT]: 2025-05-29 17:48:49 Age [y:d:h:m:s]: 00:165:05:33:47
Block: 1293636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115767 RingCT/type: yes/0
Extra: 01a4f97fdaf9d66ad5d8d720ef259a2b29efbd87adc667400ba3b16af92231ee3d021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 816384245316177bd4769fed2312c2b6317f499a3686dbe81e4b833268129a1e 0.600000000000 1781121 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": 1293646, "vin": [ { "gen": { "height": 1293636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "816384245316177bd4769fed2312c2b6317f499a3686dbe81e4b833268129a1e" } } ], "extra": [ 1, 164, 249, 127, 218, 249, 214, 106, 213, 216, 215, 32, 239, 37, 154, 43, 41, 239, 189, 135, 173, 198, 103, 64, 11, 163, 177, 106, 249, 34, 49, 238, 61, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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