Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94c16da363243a9479972150990502a12dd39fd13b1ec011dcf0253c7d638da0

Tx prefix hash: 07595c0072007f6edb2ddd7dc9e07d78b924e1f05384dba450b746ec64331671
Tx public key: 35746a81ad4e205ce7f003cb0e90fafb1feaa6b30c9ef52d00f8fccbb31922a6
Timestamp: 1703460596 Timestamp [UCT]: 2023-12-24 23:29:56 Age [y:d:h:m:s]: 01:094:23:46:05
Block: 920442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328992 RingCT/type: yes/0
Extra: 0135746a81ad4e205ce7f003cb0e90fafb1feaa6b30c9ef52d00f8fccbb31922a602110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e41d0a5ee1ba8c96b27d2ae7a98d0e019494f4ad32f33308635df35c3508b93 0.600000000000 1378120 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": 920452, "vin": [ { "gen": { "height": 920442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e41d0a5ee1ba8c96b27d2ae7a98d0e019494f4ad32f33308635df35c3508b93" } } ], "extra": [ 1, 53, 116, 106, 129, 173, 78, 32, 92, 231, 240, 3, 203, 14, 144, 250, 251, 31, 234, 166, 179, 12, 158, 245, 45, 0, 248, 252, 203, 179, 25, 34, 166, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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