Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bca6415256855d8f2c4e8e6fe123d4c805b3353ec84698e575c275131df8980

Tx prefix hash: 50d37e6a2034b406ddc3453aebb835b297b730431292df248b1161b67bf29b42
Tx public key: 444a3cb50acd59b4a6cc94667538ac65b6b6afb14c518242dc64fb13aa3ed16b
Timestamp: 1728015864 Timestamp [UCT]: 2024-10-04 04:24:24 Age [y:d:h:m:s]: 00:185:00:12:33
Block: 1124016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132005 RingCT/type: yes/0
Extra: 01444a3cb50acd59b4a6cc94667538ac65b6b6afb14c518242dc64fb13aa3ed16b02110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa1bd094b637d737f18aa1ee5d3217395a1db04738a2df8c70f86c193ef64c5c 0.600000000000 1606575 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": 1124026, "vin": [ { "gen": { "height": 1124016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa1bd094b637d737f18aa1ee5d3217395a1db04738a2df8c70f86c193ef64c5c" } } ], "extra": [ 1, 68, 74, 60, 181, 10, 205, 89, 180, 166, 204, 148, 102, 117, 56, 172, 101, 182, 182, 175, 177, 76, 81, 130, 66, 220, 100, 251, 19, 170, 62, 209, 107, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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