Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4108aa2adf7f8ae87b97fe2203d454e550cdde941f282d2d0cba2e3841190430

Tx prefix hash: 854c830ac9ce71089cec9c76abd1f0942b491bb321731a5ad7f56befaeca3290
Tx public key: f53a79724b51e0129f6454c2217ac2d7b55079c2dd4e3fe9ffe79a914dd49a1f
Timestamp: 1713985818 Timestamp [UCT]: 2024-04-24 19:10:18 Age [y:d:h:m:s]: 01:039:04:54:07
Block: 1007692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288988 RingCT/type: yes/0
Extra: 01f53a79724b51e0129f6454c2217ac2d7b55079c2dd4e3fe9ffe79a914dd49a1f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f6aac43f36f151b18712f9e5a510aba79bb3a18d72d5738c636d971380e6ab5 0.600000000000 1469116 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": 1007702, "vin": [ { "gen": { "height": 1007692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f6aac43f36f151b18712f9e5a510aba79bb3a18d72d5738c636d971380e6ab5" } } ], "extra": [ 1, 245, 58, 121, 114, 75, 81, 224, 18, 159, 100, 84, 194, 33, 122, 194, 215, 181, 80, 121, 194, 221, 78, 63, 233, 255, 231, 154, 145, 77, 212, 154, 31, 2, 17, 0, 0, 0, 1, 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