Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d68c7943d0750033507c3a687183e3a85da0eddfe0a0fe47983a40b15026bf23

Tx prefix hash: af6c814978c724cbfb4942030a814650b2c739db6d23adfd86af16238bda4971
Tx public key: 9f63e889b533a3809566c24003ed3d3a77a01bcde8f44f28b36adb4e3f433135
Timestamp: 1699386098 Timestamp [UCT]: 2023-11-07 19:41:38 Age [y:d:h:m:s]: 01:221:15:39:51
Block: 886657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419549 RingCT/type: yes/0
Extra: 019f63e889b533a3809566c24003ed3d3a77a01bcde8f44f28b36adb4e3f433135021100000004faf35c9c000000000000000000

1 output(s) for total of 0.708169622000 dcy

stealth address amount amount idx
00: c970f118059567ae504b3d5c4614392a2a1f2d41690014d02cd21f857f998cd2 0.708169622000 1342486 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": 886667, "vin": [ { "gen": { "height": 886657 } } ], "vout": [ { "amount": 708169622, "target": { "key": "c970f118059567ae504b3d5c4614392a2a1f2d41690014d02cd21f857f998cd2" } } ], "extra": [ 1, 159, 99, 232, 137, 181, 51, 163, 128, 149, 102, 194, 64, 3, 237, 61, 58, 119, 160, 27, 205, 232, 244, 79, 40, 179, 106, 219, 78, 63, 67, 49, 53, 2, 17, 0, 0, 0, 4, 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