Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61b08949b859e76bebd3afe6c847ca1d75cd7e43d3fce49f26aa9bf1c6f24a5e

Tx prefix hash: edbe5de720e8c3a656a2ff4478ed3e6ce387a6473c00a777238807d86c2f26c7
Tx public key: a1ce38d92dd86b07e10af85cdab4118a888e14170f08296f6b89dc5ff90543d8
Timestamp: 1711522166 Timestamp [UCT]: 2024-03-27 06:49:26 Age [y:d:h:m:s]: 01:026:11:28:04
Block: 987301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279867 RingCT/type: yes/0
Extra: 01a1ce38d92dd86b07e10af85cdab4118a888e14170f08296f6b89dc5ff90543d802110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f3d03c412f9962ba4cd8b68716e3ca6d10a4e7bb5e283a509298929e9e86386 0.600000000000 1447542 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": 987311, "vin": [ { "gen": { "height": 987301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f3d03c412f9962ba4cd8b68716e3ca6d10a4e7bb5e283a509298929e9e86386" } } ], "extra": [ 1, 161, 206, 56, 217, 45, 216, 107, 7, 225, 10, 248, 92, 218, 180, 17, 138, 136, 142, 20, 23, 15, 8, 41, 111, 107, 137, 220, 95, 249, 5, 67, 216, 2, 17, 0, 0, 0, 14, 89, 218, 211, 245, 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