Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3939c20aac5b4326b297587a66d7376ecb16f41e1313a146852aa6549f98aa39

Tx prefix hash: e681eb7fb8839638a1e6f2aed94dd162da3b0de30b15f542c721fe0943ce4e0c
Tx public key: 18cc11119ca494dd949e3b0edbd65518fbce3b850951eef5318d726a541fbeb2
Timestamp: 1671379360 Timestamp [UCT]: 2022-12-18 16:02:40 Age [y:d:h:m:s]: 02:174:14:27:51
Block: 655363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 646518 RingCT/type: yes/0
Extra: 0118cc11119ca494dd949e3b0edbd65518fbce3b850951eef5318d726a541fbeb202110000000a75e3f0e9000000000000000000

1 output(s) for total of 4.135331271000 dcy

stealth address amount amount idx
00: c40fc56a0d87e54e0a642913fc4fe5d74d51aacb94fd3d3dab7616b48b394244 4.135331271000 1095918 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": 655373, "vin": [ { "gen": { "height": 655363 } } ], "vout": [ { "amount": 4135331271, "target": { "key": "c40fc56a0d87e54e0a642913fc4fe5d74d51aacb94fd3d3dab7616b48b394244" } } ], "extra": [ 1, 24, 204, 17, 17, 156, 164, 148, 221, 148, 158, 59, 14, 219, 214, 85, 24, 251, 206, 59, 133, 9, 81, 238, 245, 49, 141, 114, 106, 84, 31, 190, 178, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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