Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 765a3eed70266b08a36d3596d3903a5e87b12446d8f4cf7fce12814022a084a9

Tx prefix hash: f7a21f8c50658a77596809aa279823f3c952d0ac2be68719498b2f888eff6949
Tx public key: ca6bfe57389ccf2a1da48222a8e9360ac9120b838570be37b4fe3089b98d60eb
Timestamp: 1700764518 Timestamp [UCT]: 2023-11-23 18:35:18 Age [y:d:h:m:s]: 01:136:18:54:33
Block: 898084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358920 RingCT/type: yes/0
Extra: 01ca6bfe57389ccf2a1da48222a8e9360ac9120b838570be37b4fe3089b98d60eb021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.649045109000 dcy

stealth address amount amount idx
00: 6d593fadcc3681cadf7e7dee48e6f8b541bb251d8ea3223dd7c02e505374af1a 0.649045109000 1354487 of 0

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": 898094, "vin": [ { "gen": { "height": 898084 } } ], "vout": [ { "amount": 649045109, "target": { "key": "6d593fadcc3681cadf7e7dee48e6f8b541bb251d8ea3223dd7c02e505374af1a" } } ], "extra": [ 1, 202, 107, 254, 87, 56, 156, 207, 42, 29, 164, 130, 34, 168, 233, 54, 10, 201, 18, 11, 131, 133, 112, 190, 55, 180, 254, 48, 137, 185, 141, 96, 235, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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