Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf82af4c9ed0c2f3c5947b957b762094901c56fd52bcdae6d949a1160d3d83fe

Tx prefix hash: 364742f58d20ee764f504d309049eeba587e549e26276e745964ef6714274e94
Tx public key: b615e6b4f41b9ce4679d1ef5ea2fa77e1f984ef9d9e5e769965d9bfeb848d8b3
Timestamp: 1697284287 Timestamp [UCT]: 2023-10-14 11:51:27 Age [y:d:h:m:s]: 01:132:17:20:47
Block: 869436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355841 RingCT/type: yes/0
Extra: 01b615e6b4f41b9ce4679d1ef5ea2fa77e1f984ef9d9e5e769965d9bfeb848d8b3021100000001faf35c9c000000000000000000

1 output(s) for total of 0.807602473000 dcy

stealth address amount amount idx
00: 269096d0455abec743ac7865c75cb9d06e73892d919797c0f33bc3fadcc77faf 0.807602473000 1324281 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": 869446, "vin": [ { "gen": { "height": 869436 } } ], "vout": [ { "amount": 807602473, "target": { "key": "269096d0455abec743ac7865c75cb9d06e73892d919797c0f33bc3fadcc77faf" } } ], "extra": [ 1, 182, 21, 230, 180, 244, 27, 156, 228, 103, 157, 30, 245, 234, 47, 167, 126, 31, 152, 78, 249, 217, 229, 231, 105, 150, 93, 155, 254, 184, 72, 216, 179, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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