Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa1fdb48ebfa1e2c262d5f14a387461933825f80a8d7c914d7a60022102cacd6

Tx prefix hash: f2f03d3f0939a7730d99d1e346311df2c47ae8114edc5a26028487822acde583
Tx public key: 8a50e6693619f4eb7415ea66387f473c564eefe6afb4bf66e0f9da544f8b7646
Timestamp: 1737960149 Timestamp [UCT]: 2025-01-27 06:42:29 Age [y:d:h:m:s]: 00:141:18:11:37
Block: 1206066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101237 RingCT/type: yes/0
Extra: 018a50e6693619f4eb7415ea66387f473c564eefe6afb4bf66e0f9da544f8b7646021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6379029d8166e159d596cfd4ceb91d3434c35b0dd8c8d4b88f55d80712ec5a33 0.600000000000 1692767 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": 1206076, "vin": [ { "gen": { "height": 1206066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6379029d8166e159d596cfd4ceb91d3434c35b0dd8c8d4b88f55d80712ec5a33" } } ], "extra": [ 1, 138, 80, 230, 105, 54, 25, 244, 235, 116, 21, 234, 102, 56, 127, 71, 60, 86, 78, 239, 230, 175, 180, 191, 102, 224, 249, 218, 84, 79, 139, 118, 70, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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