Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a790a8e9746b9b88bed9a9ef8a94b3159b9d0d2743a2eeeeb0deef1d98713c0e

Tx prefix hash: 5f761ab7e739dedb94b6ca5a6dd5e88dc1ce66ed6cdf9b64116eaa4304f27fd4
Tx public key: dda7c7e417f1e9e6ac2bab76fa6234ef5c33cff26568d0d1531c49975adaccbf
Timestamp: 1706397696 Timestamp [UCT]: 2024-01-27 23:21:36 Age [y:d:h:m:s]: 01:085:23:42:42
Block: 944760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322551 RingCT/type: yes/0
Extra: 01dda7c7e417f1e9e6ac2bab76fa6234ef5c33cff26568d0d1531c49975adaccbf02110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54e0b582a9e7eaeeae99b6ca602a2eee4a41c36c6f40ca275e6d8a7cf0304f64 0.600000000000 1403046 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": 944770, "vin": [ { "gen": { "height": 944760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54e0b582a9e7eaeeae99b6ca602a2eee4a41c36c6f40ca275e6d8a7cf0304f64" } } ], "extra": [ 1, 221, 167, 199, 228, 23, 241, 233, 230, 172, 43, 171, 118, 250, 98, 52, 239, 92, 51, 207, 242, 101, 104, 208, 209, 83, 28, 73, 151, 90, 218, 204, 191, 2, 17, 0, 0, 0, 13, 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