Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f900892580f085d1498d1e7b5e089f63fc9b00362550f93b27c20239ab58fda

Tx prefix hash: 0c7d94284825cb5d376dbb072c07c0d09a1976566e8db20b1f87e0c3943c6761
Tx public key: 64bfb27be1a5573d4f87a1e3cc9461624018a9d2387948ea152f3171368b926a
Timestamp: 1711702203 Timestamp [UCT]: 2024-03-29 08:50:03 Age [y:d:h:m:s]: 01:070:02:16:44
Block: 988774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311097 RingCT/type: yes/0
Extra: 0164bfb27be1a5573d4f87a1e3cc9461624018a9d2387948ea152f3171368b926a02110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65a21b2901ff801f70e5caa3e8017072d5437e71fed95ded8e45c5dd6ef4e5ea 0.600000000000 1449059 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": 988784, "vin": [ { "gen": { "height": 988774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65a21b2901ff801f70e5caa3e8017072d5437e71fed95ded8e45c5dd6ef4e5ea" } } ], "extra": [ 1, 100, 191, 178, 123, 225, 165, 87, 61, 79, 135, 161, 227, 204, 148, 97, 98, 64, 24, 169, 210, 56, 121, 72, 234, 21, 47, 49, 113, 54, 139, 146, 106, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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